⚠️ GitHub issue #48356 has been automatically assigned in GitHub to PR creator.

The MakeStructOptions class is missing the field_nullability and field_metadata properties because I ran into limitations of the gobject-introspection gem, e.g.: NotImplementedError: TODO: GIArgument(GList)[ghash] -> Ruby. I couldn't figure out what types the properties should have for it to work.

Another issue I ran into was that the ListSliceOptions property return_fixed_size_list has the type std::optional<bool>. While it would make sense in Ruby, I couldn't figure out how to set a boolean to null in GLib, so I created an enum instead.

Thanks! But could you split this large PR to smaller PRs? I can't review this...

Could you use one issue/PR per option class?

For example, I'm using #48132 is an umbrella issue for pure Ruby Apache Arrow implementation.

The MakeStructOptions class is missing the field_nullability and field_metadata properties because I ran into limitations of the gobject-introspection gem, e.g.: NotImplementedError: TODO: GIArgument(GList)[ghash] -> Ruby. I couldn't figure out what types the properties should have for it to work.

I'll implement it in the gobject-introspection gem later.

There is one commit per option class to make it easier to review. The reason I created a single PR is that 32 of the commits adds code to the same place. This means that when it is time to merge you would get conflicts for all of these. Also, two of them needs the 33rd commit (FixedSizeListArray) for the tests to pass. Do you still want me to create separate PRs?

Yes.

If you use one large PR, we can't merge this until we're ready all options. If any of them has a problem, we can't merge all of them. I can't review large PR multiple times.

You don't need to open 32 PRs at a time. You can open a few PR at once. You can open more PRs after they are merged.

That makes sense. I will close this and open separate PRs.